fix(integrations): declare kiro-cli multi-install safe#3477
fix(integrations): declare kiro-cli multi-install safe#3477Quratulain-bilal wants to merge 3 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
Declares Kiro CLI safe for co-installation and documents the behavior.
Changes:
- Enables
multi_install_safefor Kiro CLI. - Adds a regression assertion.
- Adds Kiro CLI to the safety reference table.
Show a summary per file
| File | Description |
|---|---|
src/specify_cli/integrations/kiro_cli/__init__.py |
Enables safe multi-installation. |
tests/integrations/test_integration_kiro_cli.py |
Verifies the safety declaration. |
docs/reference/integrations.md |
Documents Kiro CLI, but contains a safety-criteria inconsistency. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 3/3 changed files
- Comments generated: 1
- Review effort level: Medium
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback
|
thanks, you're right that the docs read like a contradiction — fixed the wording in 050446f. digging in though, it's not a real collision. two separate layers were getting conflated:
and that extension can't actually make two safe integrations write the same file: in so the flag is correct as-is; the docs just described a constraint ( |
|
We need to resolve by remove the agent file mention altogether. By default integrations are now multi-install safe. The agent-context extension is not. Maybe we should call that out in its README. Can you make that change? |
kiro-cli is declared multi_install_safe (it uses a fully isolated .kiro/ root, .kiro/prompts command dir, a stable '.' separator, and a dedicated manifest — github#3471). main ended up with the flag assigned twice in the class body; this drops the bare duplicate and keeps a single declaration with the comment explaining why it's safe. also adds the missing kiro-cli row to the multi-install-safe table in docs/reference/integrations.md, and a test asserting the flag is set (the registry contract tests already enforce the actual path isolation against every other safe integration).
050446f to
2f9ffd5
Compare
|
Please address Copilot feedback |
per maintainer guidance on github#3477: the Isolation table listed each integration's agent-context file (AGENTS.md, CLAUDE.md, etc.) alongside its command dir, which contradicted the safety definition (Copilot flagged kiro-cli/codex both mapping to AGENTS.md). those context files are owned by the optional agent-context extension, not by multi_install_safe — the flag governs only the command directory + manifest. - renamed the column to 'Command directory' and removed the agent-file entries, so it lists only what each integration actually manages - reworded the definition to note agent-context is a separate concern and is not multi-install safe - removed the duplicate test_declared_multi_install_safe (the existing test_declares_multi_install_safe already asserts the same thing)
|
done in 62faa8b.
on calling it out in the agent-context extension's README: happy to do that as a small follow-up PR so this one stays focused. want me to? |
…rgeting - Restore 'static, unique agent root' alongside command directory in the multi-install-safe definition — base.py and test_registry.py (test_safe_integrations_have_distinct_agent_roots) enforce both. - Reframe the agent-context note: multi_install_safe is an integration-level declaration about command/skill paths, so describe context-file targeting as independent of it rather than calling the extension 'not multi-install safe'. The extension can even sync multiple anchors via context_files.
|
Please address Copilot feedback |
|
Addressed both remaining Copilot threads in 6eaf46a:
|
| @@ -13,7 +13,6 @@ | |||
|
|
|||
| class KiroCliIntegration(MarkdownIntegration): | |||
| key = "kiro-cli" | |||
|
Please address Copilot feedback. If not applicable, please explain why. If Copilot is going in circles please also let me know ;) |
fixes #3471
kiro-cli uses a fully isolated
.kiro/root and.kiro/promptscommand dir, a stable.separator with no dynamic paths, and a dedicated install manifest — it meets every documented multi-install-safe criterion. butmulti_install_safewas never set onKiroCliIntegration, so co-installing it (e.g. alongside claude) leftspecify integration statuspermanently in ERROR (unsafe-multi-install) with no way to resolve it.--forcebypasses the install-time gate but not the status finding.fix: set
multi_install_safe = TrueonKiroCliIntegration.i verified the isolation rather than trusting the flag: the registry contract tests in
tests/integrations/test_registry.pyauto-parametrize over every declared-safe integration and check pairwise-disjoint agent roots, command dirs, and (via a real init+install) install manifests. with kiro-cli added they still all pass (365 tests), which empirically proves.kiro/doesn't collide with any other safe integration.also added an explicit
multi_install_safe is Trueassertion in the kiro-cli test file (fails on the pre-fix code) and listed kiro-cli in the multi-install-safe docs table.